Integrated security system with parallel processing architecture

ABSTRACT

An integrated security system that includes a security coprocessor coupled to a conventional security system panel and an interactive security system. The integrated security system enables conventional security system features as well as the consumer-oriented interactive features and functions of an interactive security system without sacrificing reliability or the significant burden and cost associated with frequent software updates associated with conventional security systems. The integrated security system also minimizes or eliminates the need for new battery backup circuitry or larger batteries.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/148,411, filed on Oct. 1, 2018, which is a continuation of U.S.patent application Ser. No. 14/667,060, filed on Mar. 24, 2015, issuedas U.S. Pat. No. 10,223,903 on Mar. 5, 2019, which is a continuationapplication of U.S. patent application Ser. No. 12/892,801, filed Sep.28, 2010, issued as U.S. Pat. No. 8,988,221 on Mar. 24, 2015, which arehereby incorporated by reference in their entirety.

U.S. patent application Ser. No. 12/892,801 is a continuation in partapplication of U.S. patent application Ser. No. 12/269,585, filed Nov.12, 2008, issued as U.S. Pat. No. 8,086,702 on Dec. 27, 2011,

and is a continuation in part application of U.S. patent applicationSer. No. 12/198,023, filed Aug. 25, 2008, issued as U.S. Pat. No.8,209,400 on Jun. 26, 2012,

and is a continuation in part application of U.S. patent applicationSer. No. 12/197,895, filed Aug. 25, 2008, issued as U.S. Pat. No.8,073,931 on Dec. 6, 2011,

and is a continuation in part application of U.S. patent applicationSer. No. 12/189,757, filed Aug. 11, 2008, issued as U.S. Pat. No.8,473,619 on Jun. 25, 2013,

U.S. patent application Ser. No. 12/269,585 is a non-provisional of andclaims the benefit of U.S. provisional Application No. 61/023,496, filedJan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 61/023,493, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 61/023,489, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 61/019,162, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 61/019,167, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 60/987,366, filed Nov. 12, 2007,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 60/987,359, filed Nov. 12, 2007, each of which arehereby incorporated by reference in their entirety.

U.S. patent application Ser. No. 12/198,023 is a non-provisional of andclaims the benefit of U.S. provisional Application No. 60/968,005, filedAug. 24, 2007,

and is a non-provisional of and claims the benefit of U.S. provisionalApplication No. 60/957,997, filed Aug. 24, 2007, each of which arehereby incorporated by reference in their entirety.

U.S. patent application Ser. No. 12/189,757 is a non-provisional of andclaims the benefit of U.S. provisional Application No. 60/955,172, filedAug. 10, 2007, which is hereby incorporated by reference in itsentirety.

BACKGROUND

Security alarm systems are well-known and have been around for decades.Some of the noteworthy large manufacturers of traditional security alarmsystems are Honeywell, GE, DSC and Napco. These systems generallycontain a low-power (i.e., 8-bit) processor, with no operating system,running small (i.e. tens or hundreds of kilobytes) embedded software.These security panels have a relatively compact and straightforward codebase that is easily tested and maintained because updates to theembedded software are time-consuming and costly as they would require anew certification to be performed on the overall system and/or softwarebefore the deployment of the new code. Because of this, software updatesare infrequent. These systems strive for the highest reliabilitypossible and regulatory requirements often require them to passstringent safety, reliability and fault tolerance tests before beingallowed to be certified for sale to the public.

FIG. 23 is a block diagram of a security system panel of a conventionalsecurity system 100 under the prior art. A security panel 2302 monitorsand communicates with wired and/or wireless sensors 2304, and alarmconditions are reported to a Central Monitoring Station (CMS) via aphone line 2306. The security panel 2303 is coupled to an external powersource 2310 (e.g., alternating current (AC) source, direct current (DC)source, etc.) and a battery 2308, and the battery 2308 is generallytrickle-charged by the panel 2302. The primary source of power for thesecurity panel 2302 is the external power source 2310, and in the eventof an interruption in the external power 2310, the panel 2302automatically switches to the battery 2308 as its power source.

Underwriters Laboratories® Inc. (UL) requirements dictate the minimumsystem performance required under battery operation. The ULcertification is also required for the software residing on theconventional security panel 2302 in order to meet minimum safety andreliability performance levels. As such, software updates forconventional security panels occur very infrequently as they are costlyand time consuming and involve highly-rigorous testing and regulatorycertification.

Embedded monitoring, video and automation systems are also well knownand have been around for some time. Due to the nature of their featureset they typically require larger processors and more sophisticatedinternal software to handle the more complex and bandwidth intensiveoperations. In addition, such systems are highly feature-rich andmanufacturers are continually improving existing features and adding newones in order to maintain product competitiveness. As such, thesesystems often require software updates (either performed by the user orautomatically performed in the background).

Creating a feature-rich system that combines both traditional securityas well as consumer-oriented interactive features results in a productthat is a superset of the two systems in terms of processing power andsoftware. Consequently, when providing extended monitoring andautomation features on top of such a security system, additionalprocessing power and software is required. A larger code base inherentlymakes the overall system less reliable thereby making the reliabilityrequirements imposed by security companies and security standards aneven more challenging hurdle. The additional software inherently reducesthe reliability of the overall code and introduces more software codepaths that can potentially fail. This can also be a disadvantage as itcan require the entire system to go through a security certificationprocess each time the system software is modified, even if the softwarechanges are only related to the interactive and consumer-related portionof the code. Furthermore, the battery backup of this integrated system,including the larger processor and memory, would require a largerbattery and potentially more sophisticated backup circuitry forsupporting the larger power load.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the integrated security system, under anembodiment.

FIG. 2 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 2A is a block diagram of an integrated security system comprising asecurity coprocessor (SCP), under an embodiment.

FIG. 3 is a block diagram of the gateway software or applications, underan embodiment.

FIG. 4 is a block diagram of the gateway components, under anembodiment.

FIG. 4A (collectively FIGS. 4A/1 and 4A/2) shows the orb icon andcorresponding text summary display elements, under an embodiment.

FIG. 4B is a table of security state and the corresponding sensor statusdisplayed on the SUI, under an embodiment.

FIG. 4C is a table of system state and the corresponding warning textdisplayed as system warnings on the SUI, under an embodiment.

FIG. 4D is a table of sensor state/sort order and the correspondingsensor name and status text of the SUI, under an embodiment.

FIG. 4E shows icons of the interesting sensors, under an embodiment.

FIG. 4F shows the quiet sensor icon, under an embodiment.

FIG. 4G is an example Home Management Mode (HMM) screen presented viathe web portal SUI, under an embodiment.

FIG. 4H is an example Home Management Mode (HMM) screen presented viathe mobile portal SUI, under an embodiment.

FIG. 4I is a block diagram of an iPhone® client device SUI, under anembodiment.

FIG. 4J is a first example iPhone® client device SUI, under anembodiment.

FIG. 4K is a second example iPhone® client device SUI, under anembodiment.

FIG. 4L is a block diagram of a mobile portal client device SUI, underan embodiment.

FIG. 4M is an example summary page or screen presented via the mobileportal SUI, under an embodiment.

FIG. 4N is an example security panel page or screen presented via themobile portal SUI, under an embodiment.

FIG. 4O is an example sensor status page or screen presented via themobile portal SUI, under an embodiment.

FIG. 4P is an example interface page or screen presented via the webportal SUI, under an embodiment.

FIG. 4Q is an example summary page or screen presented via thetouchscreen SUI, under an embodiment.

FIG. 4R is an example sensor status page or screen presented via thetouchscreen SUI, under an embodiment.

FIG. 5 is a block diagram of IP device integration with a premisesnetwork, under an embodiment.

FIG. 6 is a block diagram of IP device integration with a premisesnetwork, under an alternative embodiment.

FIG. 7 is a block diagram of a touchscreen, under an embodiment.

FIG. 8 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 9 is a block diagram of network or premises device integration witha premises network, under an embodiment.

FIG. 10 is a block diagram of network or premises device integrationwith a premises network, under an alternative embodiment.

FIG. 11 is a flow diagram for a method of forming a security networkincluding integrated security system components, under an embodiment.

FIG. 12 is a flow diagram for a method of forming a security networkincluding integrated security system components and network devices,under an embodiment.

FIG. 13 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 14 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 15 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 16 is a block diagram of an integrated security system wirelesslyinterfacing to proprietary security systems, under an embodiment.

FIG. 17 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

FIG. 18 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, under an embodiment.

FIG. 19 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, and a touchscreen, under an alternative embodiment.

FIG. 20 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel connected to a gatewayvia an Ethernet coupling, under another alternative embodiment.

FIG. 21 is a flow diagram for automatic takeover of a security system,under an embodiment.

FIG. 22 is a flow diagram for automatic takeover of a security system,under an alternative embodiment.

FIG. 23 is a block diagram of a security system panel of a conventionalsecurity system under the prior art.

DETAILED DESCRIPTION

An integrated security system is described that integrates broadband andmobile access and control with conventional security systems andpremises devices to provide a tri-mode security network (broadband,cellular/GSM, POTS access) that enables users to remotely stay connectedto their premises. The integrated security system, while deliveringremote premises monitoring and control functionality to conventionalmonitored premises protection, complements existing premises protectionequipment. The integrated security system integrates into the premisesnetwork and couples wirelessly with the conventional security panel,enabling broadband access to premises security systems. Automationdevices (cameras, lamp modules, thermostats, etc.) can be added,enabling users to remotely see live video and/or pictures and controlhome devices via their personal web portal or webpage, mobile phone,and/or other remote client device. Users can also receive notificationsvia email or text message when happenings occur, or do not occur, intheir home.

Although the detailed description herein contains many specifics for thepurposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the embodiments described herein. Thus, thefollowing illustrative embodiments are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premises security systemand a premises local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example,application programming interfaces (APIs) that allow the security systemprovider to integrate components of the integrated security system intoa custom call center interface. The APIs include XML web service APIsfor integration of existing security system provider call centerapplications with the integrated security system service. Allfunctionality available in the CSR Web application is provided withthese API sets. The Java and XML-based APIs of the integrated securitysystem support provisioning, billing, system administration, CSR,central station, portal user interfaces, and content managementfunctions, to name a few. The integrated security system can provide acustomized interface to the security system provider's billing system,or alternatively can provide security system developers with APIs andsupport in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate operationssupport system (OSS)/business support system (BSS) (OSS/BSS) systems ofa Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1xRTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premises and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 1 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in an integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, interne, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OSS/BSS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 2 is a block diagram ofcomponents of the integrated security system 100, under an embodiment.Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

Clients based on gateway client applications 202 (e.g., aprocessor-based device running the gateway technology that manages homesecurity and automation devices).

A web browser 204 accessing a Web Portal application, performingend-user configuration and customization of the integrated securitysystem service as well as monitoring of in-home device status, viewingphotos and video, etc. Device and user management can also be performedby this portal application.

A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing theintegrated security system Mobile Portal. This type of client 206 isused by end-users to view system status and perform operations ondevices (e.g., turning on a lamp, arming a security panel, etc.) ratherthan for system configuration tasks such as adding a new device or user.

PC or browser-based “widget” containers 208 that present integratedsecurity system service content, as well as other third-party content,in simple, targeted ways (e.g. a widget that resides on a PC desktop andshows live video from a single in-home camera). “Widget” as used hereinmeans applications or programs in the system.

Touchscreen home security keypads 208 and advanced in-home devices thatpresent a variety of content widgets via an intuitive touchscreen userinterface.

Notification recipients 210 (e.g., cell phones that receive SMS-basednotifications when certain events occur (or don't occur), email clientsthat receive an email message with similar information, etc.).

Custom-built clients (not shown) that access the iConnect web servicesXML API to interact with users' home security and self-monitoringinformation in new and unique ways. Such clients could include new typesof mobile devices, or complex applications where integrated securitysystem content is integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which a gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        gateway clients, including receiving information about device        state changes, changing the configuration of devices, and        pushing new versions of the gateway client to the hardware it is        running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMP MIBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. Pushes of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

The integrated security system of an embodiment comprises a securitycoprocessor that couples to a conventional security system panel and aninteractive security system. Under this architecture, the integratedsecurity system enables conventional security system features as well asthe consumer-oriented interactive features and functions of aninteractive security system without sacrificing reliability or thesignificant burden and cost associated with frequent software updatesassociated with conventional security systems. The integrated securitysystem also minimizes or eliminates the need for new battery backupcircuitry or larger batteries.

FIG. 2A is a block diagram of an integrated security system 200Acomprising a security coprocessor (SCP) 204A, under an embodiment. TheSCP 204A of the integrated security system 200A couples or connects to asecurity panel 202A and to an interactive security system 206A.Communication channels or paths 230A are formed between the SCP 204A andthe security panel 202A and the interactive security system 206A, andthe SCP 204A controls the communication channels 230A and therefore thecommunications among the security panel 202A and the interactivesecurity system 206A.

Wired or wireless sensors 212A (e.g., door sensor, window sensors,infrared sensors, heat sensors, smoke sensors, etc.) are monitored bythe security panel 202A, which is a component of a security system. Thesecurity panel 202A connects to the phone line for reporting alarms tothe CMS, as described above. The security panel also incorporates abattery with associated charging and switch-over circuitry.

The interactive security system 206A communicates with wired and/orwireless devices or components 216A (e.g., Internet Protocol (IP)devices, cameras, touchscreen input/output devices, thermostats,controllers, etc.). A battery 210A is coupled to the security panel 202Aand the interactive security system 206A. The integrated security system200A comprises a power switch 208A coupled to the security panel 202A,SCP 204A, and the interactive security system 206A.

The SCP 204A orchestrates the behavior of the integrated security system200A during external power interruptions. The SCP 204A also coordinatesthe communication between the security panel 202A and the processor ofthe interactive security system 206A, ensuring a stable flow of databetween these systems or components. Further examples of components,configurations and operations of the integrated security system 200A canbe found in the Related Applications.

Power flows from the external power source 220A into the security panel202A, which then controls or supplies power to the SCP 204A and, via apower switch 208A, to the interactive security system 206A processor. Inthe event of an external power failure, the security panel 202Acommunicates the failure condition to the SCP 204A. The SCP 204A signalsthe power switch 208A to turn off power to the interactive securitysystem 206A processor, thereby reducing the overall system powerconsumption. Critical power during power failures is now only applied tothe key subsystems that are required to be up and running, namely thesecurity panel 202A, the SCP 204A and the communications radio or device(e.g., Global System for Mobile Communications (GSM) radio, etc.) of theinteractive security system 206A (for backup in case the phone line goesdown).

Much like the security panel 202A, software of the SCP 204A isrelatively small and thus more easily tested and maintained. Theprocessor code of the interactive security system 206A is usuallyrelatively larger, but because it does not have to adhere to ULrequirements it can be modified and remotely updated as frequently asnecessary.

In an embodiment, the gateway described herein is or includes theinteractive security system, but the embodiment is not so limited. In analternative embodiment, the gateway described herein is or includes theinteractive security system and the security coprocessor, but theembodiment is not so limited. In another alternative embodiment, thetouchscreen described herein is or includes the interactive securitysystem, but the embodiment is not so limited. In yet another alternativeembodiment, the touchscreen described herein is or includes theinteractive security system and the security coprocessor, but theembodiment is not so limited.

FIG. 3 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A gateway-enabled device is assigned a unique activation key for        activation with an iConnect server. This ensures that only valid        gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only a gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        affect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8am settemperature to 65 degrees Fahrenheit, etc.). Though the schedules areprogrammed and reside at the iConnect server level they are sent to thescheduler within the gateway application. The Schedules Engine 318 theninterfaces with SensorConnect 312 to ensure that scheduled events occurat precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 4 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gatewayl02 , the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as back-up for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The system of an embodiment uses or includes a system user interface(SUI) that provides an iconic, at-a-glance representation of securitysystem status. The SUI is for use across all client types as describedabove with reference to FIG. 1. The SUI includes a number of displayelements that are presented across all types of client devices used tomonitor status of the security system. The clients of an embodimentinclude, but are not limited to, the iPhone , a mobile portal, a webportal, and a touchscreen. The display elements of the SUI of anembodiment include, but are not limited to, an orb icon, text summary,security button, device and system warnings, interesting sensors, andquiet sensors, as described in detail below. The SUI thus providessystem status summary information (e.g., security and sensors) uniformlyacross all clients. Additionally, the SUI provides consistenticonography, terminology, and display rules across all clients as wellas consistent sensor and system detail across clients.

Following is a description of the various states of the iControlsensors, and how these states are indicated uniformly across all clientsusing the SUI and other sensor information displays such as sensor listsand timelines. Regarding the display elements of the SUI, the orb iconvisually indicates the current arm state and sensor status of a singlesite. FIG. 4A (collectively FIGS. 4A/1 and 4A/2) shows the orb icon andcorresponding text summary display elements, under an embodiment. Acrossall clients, when sensor detail is shown in a list or timeline, state isindicated using the proper icon, text summary and grouping. The orbicons and text summary elements of an embodiment generally representsystem state 4001 to include the following states: “Disarmed” or“Subdisarmed”; “Armed (Doors and Windows, Stay, Away, All, Night Stay,Instant, Motion, Maximum)”; “Disarmed”, or “Subdisarmed” (sensor absent;sensor tripped; sensor tampered; low battery; uncleared alarm); “Armed(Doors and Windows, Stay, Away, All, Night Stay, Instant, Motion,Maximum)” (sensor absent; sensor tripped; sensor tampered; low battery);“Alarm”; and “No iHub Connection” (broadband offline, etc.) (no securitypanel connection). In addition to representing system state, the orbicons and text summary elements of an embodiment generally representsystem status 4002 to include the following status: “All Quiet”;“Motion”; “Open”; “Open & Motion”.

Using various combinations of system state 4001 and status 4002, the orbicons of an embodiment indicate or represent numerous system states.

When the system state 4001 is “Disarmed” or “Subdisarmed”, the orb iconsof an embodiment indicate or represent status 4002 as follows: Disarmed(status: all quiet) 4010 (e.g., icon color is green); Disarmed (status:motion) 4011 (e.g., icon color is green); Disarmed, (number of sensorsopen) Sensor(s) Open (status: open) 4012 (e.g., icon color is green,bottom region for sensor number is yellow); Disarmed, (number of sensorsopen) Sensor(s) Open (status: open and motion) 4013 (e.g., icon color isgreen, bottom region for sensor number is yellow).

When the system state 4001 is “Armed (Doors and Windows, Stay, Away,All, Night Stay, Instant, Motion, Maximum)”, the orb icons of anembodiment indicate or represent status 4002 as follows: Armed Doors &Windows (status: all quiet) 4014 (e.g., icon color is red); Armed Doors& Windows (status: motion) 4015 (e.g., icon color is red); Armed Doors &Windows, (number of sensors open) Sensor(s) Open (status: open) 4016(e.g., icon color is red, bottom region for sensor number is yellow);Armed Doors & Windows, (number of sensors open) Sensor(s) Open (status:open and motion) 4017 (e.g., icon color is red, bottom region for sensornumber is yellow).

When the system state 4001 is “Disarmed”, or “Subdisarmed” (sensorabsent; sensor tripped; sensor tampered; low battery; uncleared alarm),the orb icons of an embodiment indicate or represent status 4002 asfollows: Disarmed, sensor problem (status: all quiet) 4018 (e.g., iconcolor is green, badge in top region with “!” symbol is red); Disarmed,sensor problem (status: motion) 4019 (e.g., icon color is green, badgein top region with “!” symbol is red); Disarmed, sensor problem (status:open) 4020 (e.g., icon color is green, badge in top region with “!”symbol is red, bottom region for sensor number is yellow); Disarmed,sensor problem (status: open and motion) 4021 (e.g., icon color isgreen, badge in top region with “!” symbol is red, bottom region forsensor number is yellow).

When the system state 4001 is “Armed (Doors and Windows, Stay, Away,All, Night Stay, Instant, Motion, Maximum)” (sensor absent; sensortripped; sensor tampered; low battery), the orb icons of an embodimentindicate or represent status 4002 as follows: Armed Doors & Windows,sensor problem (status: all quiet) 4022 (e.g., icon color is red, badgein top region with “!” symbol is red); Armed Doors & Windows, sensorproblem (status: motion) 4023 (e.g., icon color is red, badge in topregion with “!” symbol is red); Armed Doors & Windows, sensor problem(status: open) 4024 (e.g., icon color is red, badge in top region with“!” symbol is red, bottom region for sensor number is yellow); ArmedDoors & Windows, sensor problem (status: open & motion) 4025 (e.g., iconcolor is red, badge in top region with “!” symbol is red, bottom regionfor sensor number is yellow).

When the system state 4001 is “Alarm”, the orb icons of an embodimentindicate or represent status 4002 as follows: Armed Away/Stay, (alarmtype) ALARM 4026 (e.g., icon color is red).

When the system state 4001 is “No iHub Connection” (broadband offline,etc.) (no security panel connection), the orb icons of an embodimentindicate or represent status 4002 as follows: Status Unavailable 4027(e.g., icon color is grey).

When the client of an embodiment is a touchscreen, a mini orb ispresented at the bottom of the touch screen in all widgets and settingsscreens. The mini orb is green when the security panel is disarmed, andit is red when the security panel is armed, but is not so limited. Theform factor of the mini orb, and the text corresponding to the mini orb,is the same or similar to that described above as corresponding to theorb icon on the home screen.

The orb icons of an embodiment include motion indicators that animate toindicate motion detected by a corresponding sensor or detector.Furthermore, the orb icons of an embodiment show an animation during theexit delay when arming the security system and, additionally, indicate acountdown time showing the time remaining before the security system isfully armed. Moreover, selection of the orb of an embodiment causesadditional information (e.g., list of sensors, etc.) of the securitysystem and/or premises to be displayed.

The text summary display element of the SUI includes or displaysinformation including a direct description of the current state of thesecurity system to support the visual appearance of the orb icon. In anembodiment, two phrases are shown, including a first phrase for securitystate and a second phrase for sensor status (e.g., “Armed Stay. AllQuiet”), as described herein. FIG. 4B is a table of security state andthe corresponding sensor status displayed on the SUI, under anembodiment. The possible values for the text summary are (in priorityorder): Status Unavailable; if the security panel and control box areonline and there are no current alarms, the text summary section is acombination of one phrase from each of the security state 4030 and thesensor status 4032. The security state 4030 of an embodiment is selectedfrom among the following, but is not so limited: Armed Doors & Windows;Armed All; Armed Stay; Armed Away; Disarmed; Armed Maximum; Armed NightStay; Armed Stay Instant; Armed Away Instant; Armed Motion; Subdisarmed.The sensor status 4032 of an embodiment is selected from among thefollowing, but is not so limited: Uncleared Alarm; Sensor Tripped;Sensor Problem; Sensor(s) Bypassed; Motion; All Quiet; (number ofsensors open) Sensor(s) Open.

The display elements of the SUI also include security buttons. Thesecurity buttons are used to control or arm/disarm the security panel. Asingle arm button (e.g., button labeled “Arm”) can be used on the SUI ofa first client device type (e.g., Touchscreen, iPhone®, etc.). Twodifferent buttons (e.g., buttons labeled “Arm Away/Arm Stay” or “ArmAll/Doors and Windows”) can be used on the SUI of a second client devicetype (e.g., web portal, mobile portal, etc.). In either embodiment, whenthe system is armed, the arm button (e.g., “Arm”, “Arm Stay” and “ArmAway”) label will change to a “Disarm” label. If the system is in theprocess of arming, the button is disabled.

The display elements of the SUI include system and device warnings, asdescribed above. The system and device warning are informationalwarnings that are not associated with specific sensors, and involve moredetail than can be displayed in the text summary display element. FIG.4C is a table of system state and the corresponding icons and warningtext displayed as system warnings on the SUI, under an embodiment. Wherean icon is displayed, an embodiment uses a red color for the icon, butit is not so limited. The system states/warnings of an embodimentinclude, but are not limited to, the following: primary connection isbroadband, broadband is down, cellular is being used/using cellularconnection; primary connection is broadband, broadband and cellular aredown/no cellular connection; primary connection is broadband, broadbandis down, no cellular backup installed/broadband connection unknown;primary connection is cellular, cellular is down/no cellular connection;security panel not connected to AC power/security panel AC power loss;security panel low battery/security panel low battery; security paneltampered/security panel tampered; sensor(s) bypassed/sensor bypassed.

The device warnings of an embodiment include, but are not limited to,the following: camera(s) offline; light(s) offline; thermostat(s)offline. The device and system warnings may be combined into one box, orindicated separately in respective regions or portions of the SUI,depending on a type of the client device (e.g., combined into one box ona web portal or a mobile portal, but indicated in separate boxes on aTouchscreen or iPhone® device).

The device and system warnings display element is cumulative (e.g.,built up in a list), but is not so limited. On the web and mobileportals the system and device warnings of an embodiment are combinedinto one area, but are not so limited. On the touchscreen device andmobile phone (e.g., iPhone), device warnings are indicated separately sothat, in an embodiment, the iPhone® tab bar and the touchscreen homescreen indicate device warnings with icon badges, and system warningsare placed on the sensors screen.

The list of all sensors includes, but is not limited to, door/windowsensors, motion detectors, smoke, flood, fire, glass break, etc. Thelist of all sensors of an embodiment does not include cameras or locks,or non-security related devices such as lights, thermostats, energy,water etc. The list of sensors is split into groups that, in anembodiment, include interesting sensors as a first group, and quietsensors as a second group. The interesting sensor group is positionedabove or sorted to the top portion of the sensor list and the quietsensors are sorted to the bottom portion of the sensor list. Any sensorthat is triggered (e.g. open, motion, etc.) is categorized as aninteresting sensor and placed in the interesting sensor group and list.Additionally, other sensor states such as tampered, tripped, absent,installing, low battery, or bypassed make a sensor “interesting”regardless of their state.

FIG. 4D is a table of sensor state/sort order and the correspondingicon, sensor name and status text of the SUI, under an embodiment.Generally, the list of interesting sensors is sorted according to thefollowing categories: motion; open/tripped; tampered; low battery;offline; installing; bypassed. Sensors are sorted alphabetically bysensor name within each category or interest type when multipleinteresting sensors have the same state. The sensor state/sort order ofan embodiment includes, but is not limited to, the following: breached &any sensor state (e.g., red icon) (interesting sensor); tripped (smoke,water, gas, freeze, etc.) (e.g., red icon) (interesting sensor);tampered (e.g., red icon) (interesting sensor); low battery (e.g., redicon) (interesting sensor); offline/AWOL (e.g., red icon) (interestingsensor); unknown (if the iHub or Security Panel is offline, all sensorshave a grey diamond icon and “Unknown” for the status text) (e.g., greyicon) (interesting sensor); installing (e.g., grey icon) (interestingsensor); open (e.g., yellow icon) (interesting sensor); motion (e.g.,yellow icon) (interesting sensor); bypassed (e.g., yellow or green icon)(interesting sensor); okay, closed, no motion (e.g., green icon) (quietsensor).

The interesting sensors are shown or displayed with an icon. FIG. 4Eshows icons of the interesting sensors, under an embodiment. A reddiamond bang icon represents tamper, offline, bypassed, installing,and/or battery. A yellow triangle icon represents open or triggered. Awavy lines icon represents motion. It is possible for an interestingsensor to have a green/closed icon (e.g., any quiet sensor that has beenbypassed).

Following the state icon and the sensor name an embodiment displaysstatus text. The status of an embodiment includes, but is not limitedto, the following: ALARM, (sensor state); tripped; tampered, (sensorstate); low battery, (sensor state); offline; unknown; installing;bypassed, (sensor state). If a sensor is offline or tampered, it willshow that text; otherwise the status text will show the tripped state:open, motion, tripped, etc. In addition, if a sensor is bypassed itsstate is “Bypassed, (sensor state)”. For example, a bypassed motionsensor that has recently detected motion would have the status: “Motion,bypassed”. If a sensor has a low battery its state does not change, butit still joins the interesting sensors group.

The quiet sensors include the remaining sensors that are not currentlyactive, and so are not categorized as interesting sensors. Quiet sensorstates of an embodiment include closed, no motion or otherwise nottripped or faulted. FIG. 4F shows the quiet sensor icon, under anembodiment. A green circle icon is a quiet sensor icon in an embodiment,and represents closed/no motion/okay/quiet. In addition to the stateicon and sensor name, each quiet sensor shows status text as follows: ifa door/window sensor is closed its state is “closed”; if a motion sensorhas not recently detected motion then its state is “no motion”; othersensors, such as a smoke detector, indicate “quiet” or “okay”. Quietsensors are listed alphabetically.

The SUI of an embodiment includes control icons for a Home ManagementMode (HMM). If the user deselects the “Set home management modesautomatically” setting via the web portal, then the Home Management Mode(HMM) screen will appear in the web and mobile Portals. FIG. 4G is anexample Home Management Mode (HMM) screen presented via the web portalSUI, under an embodiment. The HMM screen includes an orb icon andcorresponding text summary display elements, along with security buttonsthat control or arm/disarm the security panel. Furthermore, the HMMscreen includes sensor status information (e.g., “Door”, status is“open”, icon is yellow; “Basement Motion”, status is “motion”, icon isyellow; “Family Room North Motion”, status is “motion”, icon is yellow;“Water”, status is “okay”, icon is green).

FIG. 4H is an example Home Management Mode (HMM) screen presented viathe mobile portal SUI, under an embodiment. The MINI screen of themobile portal includes an orb icon and corresponding text summarydisplay elements, along with security buttons that control or arm/disarmthe security panel.

The SUI of an embodiment is supported on numerous client types, forexample, mobile telephones (e.g., iPhone®, etc.), client access viamobile portal, client access via web portal, and touchscreen to name afew. All clients types supported in an embodiment have the same statusrelated sections, but their locations change slightly depending on theclient. The status related sections of an embodiment include thefollowing: orb; arm state/sensor summary; change mode; device summaryand system warnings; interesting sensors; and quiet sensors.

FIG. 4I is a block diagram of an iPhone® client device SUI, under anembodiment. The client interface of the iPhone®, as one example client,has the orb on the security page. The text summary is below the orb. Thesecurity button (e.g., arm, disarm, etc.) is below the text summary. Atab bar is presented at the bottom of the screen. The SUI of anembodiment represents device warnings by the icons in the bottomhorizontal tab bar. If a camera, light, lock, or thermostat is offlinethen a red circle will badge the corresponding icon in the tab bar. Thenumber of offline devices is shown in the badge. FIG. 4J is a firstexample iPhone® client device SUI, under an embodiment. In this firstexample screenshot, the security page indicates one camera is offline,as indicated by the “1” in a “circle” badge displayed corresponding tothe “camera” icon in the tab bar.

System warnings appear as a group in an area (e.g., yellow area) at thetop of the sensor status screen. This area at the top of the sensorstatus screen appears only when there is a device or system warning;otherwise, it is not presented. Multiple messages appear as a verticallist with one message on each line. The yellow bar will grow in lengthto fit additional messages. If there are no system warnings then theinteresting sensors group is at the top of the sensor status screen.Interesting sensors are presented below system warnings. Quiet sensorsare presented below interesting sensors. FIG. 4K is a second exampleiPhone® client device SUI, under an embodiment. In this second examplescreenshot, the sensor status page indicates at least one sensor isbypassed, as indicated by the “Sensor(s) bypassed” message displayed atthe top of the sensor status screen.

FIG. 4L is a block diagram of a mobile portal client device SUI, underan embodiment. The mobile portal of an embodiment comprises three (3)pages or screens presented to the client, including a summary page(“summary”) , a security panel page (“security panel”), and a sensorstatus page (“sensors status”), but the embodiment is not so limited.The client interface of the mobile portal, as one example client, hasthe orb at the top of the summary page below the site name. The textsummary is below the orb. The security buttons (e.g., arm, disarm, etc.)(plural on mobile portal) are on the security panel page (accessible viathe “Security” link on the summary page). Device and system warnings arepresented in an area (e.g., yellow area) below the text summary; in anembodiment this area is presented only when device or system warningsare present. Interesting sensors presented are at the top of the sensorstatus page. Quiet sensors are presented below interesting sensors onthe sensor status page.

FIG. 4M is an example summary page or screen presented via the mobileportal SUI, under an embodiment. FIG. 4N is an example security panelpage or screen presented via the mobile portal SUI, under an embodiment.FIG. 4O is an example sensor status page or screen presented via themobile portal SUI, under an embodiment.

FIG. 4P is an example interface page or screen presented via the webportal SUI, under an embodiment. The client interface of the web portal,as one example client, has the orb in the center of the security widget.The text summary is below the orb. The security button (plurality in theweb portal) is adjacent to the orb's right side. System warnings arepresented in an area (e.g., yellow area) below the text summary; in anembodiment this area is presented only when device or system warningsare present. Multiple system warning messages are presented as avertical list with one message on each line, and the area dedicated tothe system warnings grows in length to accommodate additional messages.Interesting sensors span across the entire security widget below thetext summary. Quiet sensors span across the entire security widget belowinteresting sensors.

FIG. 4Q is an example summary page or screen presented via thetouchscreen SUI, under an embodiment. The summary page of thetouchscreen, as one example, has the orb in the center of the securitybar. The text summary is split into sections or parts on each side ofthe orb. The security button is presented on the right side of thesecurity bar.

In addition to the orb, text summary, and security button, the summarypage also includes one or more icons that enable a transfer of contentto and from the remote network, as described in detail herein. Thetouchscreen integrates the content with access and control of thesecurity system. The content includes interactive content in the form ofinternet widgets. The summary page of an embodiment also comprises atleast one icon enabling communication and control of the premisesdevices coupled to the subnetwork. The summary page also comprises oneor more icons enabling access to live video from a camera, wherein thecamera is an Internet Protocol (IP) camera.

FIG. 4R is an example sensor status page or screen presented via thetouchscreen SUI, under an embodiment. The sensor status page of thetouchscreen, as one example, displays widget badges or iconsrepresenting device warnings. System warnings are at the top of thesensor status screen; in an embodiment this area is presented only whensystem warnings are present. Multiple system warning messages arepresented as a vertical list with one message on each line, and the areadedicated to the system warnings grows in length to accommodateadditional messages. Interesting sensors are below system warnings.Quiet sensors are below interesting sensors. The sensors screen alsoincludes the mini-orb which indicates the arm state with text and color.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 5 is a block diagram 500 of network or premises device integrationwith a premises network 250, under an embodiment. In an embodiment,network devices 255, 257, 556 are coupled to the gateway 102 using asecure network coupling or connection such as SSL over an encrypted802.11 link (utilizing for example WPA-2 security for the wirelessencryption). The network coupling or connection between the gateway 102and the network devices 255, 257, 556 is a private coupling orconnection in that it is segregated from any other network couplings orconnections. The gateway 102 is coupled to the premises router/firewall552 via a coupling with a premises LAN 250. The premises router/firewall552 is coupled to a broadband modem 251, and the broadband modem 251 iscoupled to a WAN 200 or other network outside the premises. The gateway102 thus enables or forms a separate wireless network, or sub-network,that includes some number of devices and is coupled or connected to theLAN 250 of the host premises. The gateway sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The gateway 102 manages or controls the sub-network separately fromthe LAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 554 can be coupled to the LAN 250without being coupled to the gateway 102.

FIG. 6 is a block diagram 600 of network or premises device integrationwith a premises network 250, under an alternative embodiment. Thenetwork or premises devices 255, 257, 556 are coupled to the gatewayl02.The network coupling or connection between the gateway 102 and thenetwork devices 255, 257, 556 is a private coupling or connection inthat it is segregated from any other network couplings or connections.The gateway 102 is coupled or connected between the premisesrouter/firewall 552 and the broadband modem 251. The broadband modem 251is coupled to a WAN 200 or other network outside the premises, while thepremises router/firewall 552 is coupled to a premises LAN 250. As aresult of its location between the broadband modem 251 and the premisesrouter/firewall 552, the gateway 102 can be configured or function asthe premises router routing specified data between the outside network(e.g., WAN 200) and the premises router/firewall 552 of the LAN 250. Asdescribed above, the gateway 102 in this configuration enables or formsa separate wireless network, or sub-network, that includes the networkor premises devices 255, 257, 556 and is coupled or connected betweenthe LAN 250 of the host premises and the WAN 200. The gatewaysub-network can include, but is not limited to, any number of network orpremises devices 255, 257, 556 like WiFi IP cameras, security panels(e.g., IP-enabled), and security touchscreens, to name a few. Thegateway 102 manages or controls the sub-network separately from the LAN250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 554 can be coupled to the LAN 250without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premisesnetwork.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premises. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premises may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premises security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premises securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the form of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premises networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisessecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 7 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premises security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premises security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with thepremises security system, these applications make use of the samefundamental application facilities as any other ‘widget’, applicationfacilities that include graphical layout, interactivity, applicationhandoff, screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 7, the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 8 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premises alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or componets (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests; although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisessecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of alogorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 5 and 6 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3. In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the touchscreen and        iConnect server in order to prevent unauthorized spoofing and        attacks. Data sent from the iConnect server to the gateway        application (or vice versa) is digitally signed as an additional        layer of security. Digital signing provides both authentication        and validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The touchscreen provides for        128-bit SSL encapsulation of the user picture and video data        sent over the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A touchscreen-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying touchscreen-enabled        devices have the knowledge that only a gateway with the correct        serial number and activation key can be activated for use with        an iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen touchscreen includes definitions ofall supported devices (e.g., cameras, security panels, sensors, etc.)using a standardized plug-in architecture. The DeviceConnect module 310offers an interface that can be used to quickly add support for any newdevice as well as enabling interoperability between devices that usedifferent technologies/protocols. For common device types, pre-definedsub-modules have been defined, making supporting new devices of thesetypes even easier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8am set temperature to 65 degrees Fahrenheit, etc.). Thoughthe schedules are programmed and reside at the iConnect server levelthey are sent to the scheduler within the gateway application of thetouchscreen. The Schedules Engine 318 then interfaces with SensorConnect312 to ensure that scheduled events occur at precisely the desired time.

The Device Management module 320 of the touchscreen is in charge of alldiscovery, installation and configuration of both wired and wireless IPdevices (e.g., cameras, etc.) coupled or connected to the system.Networked IP devices, such as those used in the integrated securitysystem, require user configuration of many IP and security parameters,and the device management module of an embodiment handles the details ofthis configuration. The device management module also manages the videorouting module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing. The video routing engine is described in detail inthe Related Applications.

FIG. 9 is a block diagram 900 of network or premises device integrationwith a premises network 250, under an embodiment. In an embodiment,network devices 255, 556, 957 are coupled to the touchscreen 902 using asecure network connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption), andthe touchscreen 902 coupled to the premises router/firewall 552 via acoupling with a premises LAN 250. The premises router/firewall 552 iscoupled to a broadband modem 251, and the broadband modem 251 is coupledto a WAN 200 or other network outside the premises. The touchscreen 902thus enables or forms a separate wireless network, or sub-network, thatincludes some number of devices and is coupled or connected to the LAN250 of the host premises. The touchscreen sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and IP devices, to name a few. Thetouchscreen 902 manages or controls the sub-network separately from theLAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 554 can be coupled to the LAN 250without being coupled to the touchscreen 902.

FIG. 10 is a block diagram 1000 of network or premises deviceintegration with a premises network 250, under an alternativeembodiment. The network or premises devices 255, 556, 1057 are coupledto the touchscreen 1002, and the touchscreen 1002 is coupled orconnected between the premises router/firewall 552 and the broadbandmodem 251. The broadband modem 251 is coupled to a WAN 200 or othernetwork outside the premises, while the premises router/firewall 552 iscoupled to a premises LAN 250. As a result of its location between thebroadband modem 251 and the premises router/firewall 552, thetouchscreen 1002 can be configured or function as the premises routerrouting specified data between the outside network (e.g., WAN 200) andthe premises router/firewall 552 of the LAN 250. As described above, thetouchscreen 1002 in this configuration enables or forms a separatewireless network, or sub-network, that includes the network or premisesdevices 255, 556, 1057 and is coupled or connected between the LAN 250of the host premises and the WAN 200. The touchscreen sub-network caninclude, but is not limited to, any number of network or premisesdevices 255, 556, 1057 like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The touchscreen1002 manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 554 can be coupled to the LAN 250 without being coupled to thetouchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

The gateway of an embodiment, as described herein, enables couplings orconnections and thus the flow of information between various componentsof the host premises and various types and/or combinations of IPdevices, where the components of the host premises include a network, asecurity system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

FIG. 11 is a flow diagram for a method 1100 of forming a securitynetwork including integrated security system components, under anembodiment. Generally, the method comprises coupling 1102 a gatewaycomprising a connection management component to a local area network ina first location and a security server in a second location. The methodcomprises forming 1104 a security network by automatically establishinga wireless coupling between the gateway and a security system using theconnection management component. The security system of an embodimentcomprises security system components located at the first location. Themethod comprises integrating 1106 communications and functions of thesecurity system components into the security network via the wirelesscoupling.

FIG. 12 is a flow diagram for a method 1200 of forming a securitynetwork including integrated security system components and networkdevices, under an embodiment. Generally, the method comprises coupling1202 a gateway to a local area network located in a first location and asecurity server in a second location. The method comprises automaticallyestablishing 1204 communications between the gateway and security systemcomponents at the first location, the security system including thesecurity system components. The method comprises automaticallyestablishing 1206 communications between the gateway and premisesdevices at the first location. The method comprises forming 1208 asecurity network by electronically integrating, via the gateway,communications and functions of the premises devices and the securitysystem components.

In an example embodiment, FIG. 13 is a flow diagram 1300 for integrationor installation of an IP device into a private network environment,under an embodiment. The IP device includes any IP-capable device which,for example, includes the touchscreen of an embodiment. The variables ofan embodiment set at time of installation include, but are not limitedto, one or more of a private SSID/Password, a gateway identifier, asecurity panel identifier, a user account TS, and a Central MonitoringStation account identification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1302 the gateway and initiating 1304 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1306 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1308 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1310data as appropriate to the devices. Once selected, the devices areconfigured 1312 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1314 with the integrated security system servers.

The installer switches 1316 the gateway to an operational mode, and thegateway instructs or directs 1318 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1320to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1322 the newaddresses. The devices with the new addresses are then operational 1324on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxEthernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 14 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1403, gateway1402 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device which comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 14, the touchscreen 1403 incorporates an application1410 that is implemented as computer code resident on the touchscreenoperating system, or as a web-based application running in a browser, oras another type of scripted application (e.g., Flash, Java, VisualBasic, etc.). The touchscreen core application 1410 represents thisapplication, providing user interface and logic for the end user tomanage their security system or to gain access to networked informationor content (Widgets). The touchscreen core application 1410 in turnaccesses a library or libraries of functions to control the localhardware (e.g. screen display, sound, LEDs, memory, etc.) as well asspecialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1403 communicates to the gateway 1402, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1410 accesses the remote service APIs 1412 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1412 implement one ormore of the following functions, but the embodiment is not so limited:Armstate =setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”);sensorState=getSensors(type=“ALL|SensorName|SensorNameList”);result=setSensorState(SensorName, parameters=“Option1, Options2, . . .Option n”); interruptHandler=SensorEvent( ) and,interruptHandler=alarmEvent( ).

Functions of the remote service APIs 1412 of an embodiment use a remotePanelConnect API 1424 which which resides in memory on the gateway 1402.The touchscreen 1403 communicates with the gateway 1402 through asuitable network interface such as an Ethernet or 802.11 RF connection,for example. The remote PanelConnect API 1424 provides the underlyingSecurity System Interfaces 1426 used to communicate with and control oneor more types of security panel via wired link 1430 and/or RF link 3.The PanelConnect API 1224 provides responses and input to the remoteservices APIs 1426, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1224 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1403 implements the samePanelConnect API 1414 locally on the Touchscreen 1403, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1403, instead of the gateway 1402, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1403incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1402 or theTouchscreen 1403 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanell); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1410 calls functions in the remote service APIs 1412 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

FIG. 15 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1510, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1520 a software and RFsequence to locate the extant security system. The gateway and installerinitiate and complete 1530 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1540 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1540 ofsensors and has been integrated 1550 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1550 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1560 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired, or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1570enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/WL/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/WL/Javascript/Java/AJAX presentationof a monitoring and control application, enabling users to combine themonitoring and control of the extant security system and sensors withthe monitoring and control of non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 16 is a block diagram of an integrated security system 1600wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1610 is coupled or connected to a Gateway1620, and from Gateway 1620 coupled or connected to a plurality ofinformation and content sources across a network 1630 including one ormore web servers 1640, system databases 1650, and applications servers1660. While in one embodiment network 1630 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1630 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or a non-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1610 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the integratedsecurity system 1600 of this example, security system 1610 includes anRF-capable wireless security panel (WSP) 1611 that acts as the mastercontroller for security system 1610. Well-known examples of such a WSPinclude the GE Security Concord, Networx, and Simon panels, theHoneywell Vista and Lynx panels, and similar panesl from DSC and Napco,to name a few. A wireless module 1614 includes the RF hardware andprotocol software necessary to enable communication with and control ofa plurality of wireless devices 1613. WSP 1611 may also manage wireddevices 1614 physically connected to WSP 1611 with an RS232 or RS485 orEthernet connection or similar such wired interface.

In an implementation consistent with the systems and methods describedherein, Gateway 1620 provides the interface between security system 1610and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1620 communicates with an external web server 1640,database 1650, and application server 1660 over network 1630 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1620 includes server connection manager 1621, asoftware interface module responsible for all server communication overnetwork 1630. Event manager 1622 implements the main event loop forGateway 1620, processing events received from device manager 1624(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1622 further processes events and control messages fromand to security system 1610 by utilizing WSP manager 1623.

WSP manager 1623 and device manager 1624 both rely upon wirelessprotocol manager 1626 which receives and stores the proprietary orstandards-based protocols required to support security system 1610 aswell as any other devices interfacing with gateway 1620. WSP manager1623 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1610 stored in the WSP DBclient database associated with wireless protocol manager 1626. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1610.Wireless Transceiver hardware modules 1625 are then used to implementthe physical RF communications link to such devices and security systems1610. An illustrative wireless transceiver 1625 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1670 represents the 319.5 MHz RFcommunication link, enabling gateway 1620 to monitor and control WSP1611 and associated wireless and wired devices 1613 and 1614,respectively.

In one embodiment, server connection manager 1621 requests and receivesa set of wireless protocols for a specific security system 1610 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1626. WSP manager 1623 then utilizes such protocols fromwireless protocol manager 1626 to initiate the sequence of processesdetailed in FIG. 15 and FIG. 16 for learning gateway 1620 into securitysystem 1610 as an authorized control device. Once learned in, asdescribed with reference to FIG. 16 (and above), event manager 1622processes all events and messages detected by the combination of WSPmanager 1623 and the GE Security wireless transceiver module 1625.

In another embodiment, gateway 1620 incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1620 incorporates a wired interface tosecurity system 1610, and incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 16, one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1620 described herein could beintegrated completely within an existing security system 1610. In suchan embodiment, the architecture could be directly integrated with asecurity system 1610 in a manner consistent with the currently describedembodiments.

FIG. 17 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1620 with security system1610. Gateway 1620 powers up 1710 and initiates software sequences 1720and 1725 to identify accessible WSPs 1611 and wireless devices 1613,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1620). Once identified, WSP 1611 is manually or automaticallyset into ‘learn mode’ 1730, and gateway 1620 utilizes availableprotocols to add 1740 itself as an authorized control device in securitysystem 1610. Upon successful completion of this task, WSP 1611 ismanually or automatically removed from ‘learn mode’ 1750.

Gateway 1620 utilizes the appropriate protocols to mimic 1760 the firstidentified device 1614. In this operation gateway 1620 identifies itselfusing the unique or pseudo-unique identifier of the first found device1614, and sends an appropriate change of state message over RF Link1670. In the event that WSP 1611 responds to this change of statemessage, the device 1614 is then added 1770 to the system in database1650. Gateway 1620 associates 1780 any other information (such as zonename or token-based identifier) with this device 1614 in database 1650,enabling gateway 1620, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1611 does not respond to the change of statemessage, the device 1614 is not added 1770 to the system in database1650, and this device 1614 is identified as not being a part of securitysystem 1610 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1785 operations 1760, 1770, 1780 for alldevices 1614 if applicable. Once all devices 1614 have been tested inthis way, the system begins operation 1790.

In another embodiment, gateway 1620 utilizes a wired connection to WSP1611, but also incorporates a wireless transceiver 1625 to communicatedirectly with devices 1614. In this embodiment, operations under 1720above are removed, and operations under 1740 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1610.

A description of an example embodiment follows in which the Gateway(FIG. 16, element 1620) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 16, element 1610) is a Dialog system and the WSP(FIG. 16, element 1611) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 16, element 1620) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2, element 260) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/ windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ ID.

An installation and enrollment procedure of a security system includinga gateway is described below as one example of the installation process.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the provider for assignment to an            installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with Basic and/or Advanced starter kits.            He/she also keeps a stock of individual sensors, cameras,            iHubs, Simon XTs, etc. Optionally, the installer can also            stock homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            pulls out the Basic kit. The installer determines sensor            locations from a tour of the premises and discussion with            the homeowner. At this point assume the homeowner requests            additional equipment including an extra camera, two (2)            additional door/window sensors, one (1) glass break            detector, and one (1) smoke detector.        -   d. Installer mounts SimonXT in the kitchen or other location            in the home as directed by the homeowner, and routes the            phone line to Simon XT if available. GPRS and Phone numbers            pre-programmed in SimonXT to point to the provider Central            Monitoring Station (CMS).        -   e. Installer places gateway in the home in the vicinity of a            router and cable modem. Installer installs an ethernet line            from gateway to router and plugs gateway into an electrical            outlet.    -   2. Associate and Enroll gateway into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer for            kit ID (on box's barcode label).        -   c. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add gateway            as a wireless keypad. It is noted that this step is for            security only and can be automated in an embodiment.        -   d. Installer enters the installer code into the Simon XT.            Installer Learns ‘gateway’ into the panel as a wireless            keypad as a group 1 device.        -   e. Installer goes back to Web portal, and clicks the            ‘Finished Adding SimonXT’ button.    -   3. Enroll Sensors into SimonXT via iControl        -   a. All devices in the Basic kit are already associated with            the user's account.        -   b. For additional devices, Installer clicks ‘Add Device’ and            adds the additional camera to the user's account (by typing            in the camera ID/Serial #).        -   c. Installer clicks ‘Add Device’ and adds other sensors            (two (2) door/window sensors, one (1) glass break sensor,            and one (1) smoke sensor) to the account (e.g., by typing in            IDs).        -   d. As part of Add Device, Installer assigns zone, name, and            group to the sensor. Installer puts appropriate Zone and            Name sticker on the sensor temporarily.        -   e. All sensor information for the account is pushed or            otherwise propagated to the iConnect server, and is            available to propagate to CMS automation software through            the CMS application programming interface (API).        -   f. Web interface displays ‘Installing Sensors in System . .            . ’ and automatically adds all of the sensors to the Simon            XT panel through the GE RF link.        -   g. Web interface displays ‘Done Installing’—>all sensors            show green.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location, and removes the stickers.        -   b. Installer physically mounts WiFi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer goes to Web interface and is prompted for            automatic camera install. Each camera is provisioned as a            private, encrypted Wifi device on the gateway secured            sandbox network, and firewall NAT traversal is initiated.            Upon completion the customer is prompted to test the            security system.        -   d. Installer selects the ‘Test System’ button on the web            portal—the SimonXT is put into Test mode by the gateway over            GE RF.        -   e. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   f. gateway sends test data directly to CMS over broadband            link, as well as storing the test data in the user's account            for subsequent report generation.        -   g. Installer exits test mode from the Web portal.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the iControl web and mobile        portals. Customer creates a username/password at this time.    -   6. Installer instructs customer how to change Simon XT user code        from the Web interface. Customer changes user code which is        pushed to SimonXT automatically over GE RF.

An installation and enrollment procedure of a security system includinga gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the security system provider for            assignment to an installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with individual sensors, cameras, iHubs,            Simon XTs, etc. Optionally, the installer can also stock            homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            analyzes the house and talks with the homeowner to determine            sensor locations. At this point assume the homeowner            requests three (3) cameras, five (5) door/window sensors,            one (1) glass break detector, one (1) smoke detector, and            one (1) keyfob.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home. The installer routes a phone line to Simon XT if        available. GPRS and Phone numbers are pre-programmed in SimonXT        to point to the provider CMS.        -   e. Installer places gateway in home in the vicinity of a            router and cable modem, and installs an ethernet line from            gateway to the router, and plugs gateway into an electrical            outlet.    -   2. Associate and Enroll gateway into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with an installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer to add            devices.        -   c. Installer types in ID of gateway, and it is associated            with the user's account.        -   d. Installer clicks ‘Add Device’ and adds the cameras to the            user's account (by typing in the camera ID/Serial #).        -   e. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add gateway            as a wireless keypad.        -   f. Installer goes to Simon XT and enters the installer code            into the Simon XT. Learns ‘gateway’ into the panel as a            wireless keypad as group 1 type sensor.        -   g. Installer returns to Web portal, and clicks the ‘Finished            Adding SimonXT’ button.        -   h. Gateway now is alerted to all subsequent installs over            the security system RF.    -   3. Enroll Sensors into SimonXT via iControl        -   a. Installer clicks ‘Add Simon XT Sensors’—Displays            instructions for adding sensors to Simon XT.        -   b. Installer goes to Simon XT and uses Simon XT install            process to add each sensor, assigning zone, name, group.            These assignments are recorded for later use.        -   c. The gateway automatically detects each sensor addition            and adds the new sensor to the integrated security system.        -   d. Installer exits install mode on the Simon XT, and returns            to the Web portal.        -   e. Installer clicks ‘Done Adding Devices’.        -   f. Installer enters zone/sensor naming from recorded notes            into integrated security system to associate sensors to            friendly names.        -   g. All sensor information for the account is pushed to the            iConnect server, and is available to propagate to CMS            automation software through the CMS API.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location.        -   b. Installer physically mounts Wifi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer puts SimonXT into Test mode from the keypad.        -   d. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   e. Installer exits test mode from the Simon XT keypad.        -   f. Installer returns to web interface and is prompted to            automatically set up cameras. After waiting for completion            cameras are now provisioned and operational.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the integrated security system        web and mobile portals. Customer creates a username/password at        this time.    -   6. Customer and Installer observe that all sensors/cameras are        green.    -   7. Installer instructs customer how to change Simon XT user code        from the keypad. Customer changes user code and stores in        SimonXT.    -   8. The first time the customer uses the web portal to Arm/Disarm        system the web interface prompts the customer for the user code,        which is then stored securely on the server. In the event the        user code is changed on the panel the web interface once again        prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

In addition to the configurations described above, the gateway of anembodiment supports takeover configurations in which it is introduced oradded into a legacy security system. A description of example takeoverconfigurations follow in which the security system (FIG. 2, element 210)is a Dialog system and the WSP (FIG. 2, element 211) is a GE Concordpanel (e.g., equipped with POTS, GE RF, and Superbus 2000 RS485interface (in the case of a Lynx takeover the Simon XT is used)available from General Electric Security. The gateway (FIG. 2, element220) in the takeover configurations is an iHub (e.g., equipped withbuilt-in 802.11b/g router, Ethernet Hub, GSM/GPRS card, RS485 inteface,and iControl Honeywell-compatible RF card) available from iControlNetworks, Palo Alto, Calif. While components of particular manufacturersare used in this example, the embodiments are not limited to thesecomponents or to components from these vendors.

The security system can optionally include RF wireless sensors (e.g., GEwireless sensors utilizing the GE Dialog RF technology), IP cameras, aGE-iControl Touchscreen (the touchscreen is assumed to be an optionalcomponent in the configurations described herein, and is thus treatedseparately from the iHub; in systems in which the touchscreen is acomponent of the base security package, the integrated iScreen(available from iControl Networks, Palo Alto, Calif.) can be used tocombine iHub technology with the touchscreen in a single unit), andZ-Wave devices to name a few.

The takeover configurations described below assume takeover by a “new”system of an embodiment of a security system provided by another thirdparty vendor, referred to herein as an “original” or “legacy” system.Generally, the takeover begins with removal of the control panel andkeypad of the legacy system. A GE Concord panel is installed to replacethe control panel of the legacy system along with an iHub with GPRSModem. The legacy system sensors are then connected or wired to theConcord panel, and a GE keypad or touchscreen is installed to replacethe control panel of the legacy system. The iHub includes the iControlRF card, which is compatible with the legacy system. The iHub finds andmanages the wireless sensors of the legacy system, and learns thesensors into the Concord by emulating the corresponding GE sensors. TheiHub effectively acts as a relay for legacy wireless sensors.

Once takeover is complete, the new security system provides ahomogeneous system that removes the compromises inherent in taking overor replacing a legacy system. For example, the new system provides amodern touchscreen that may include additional functionality, newservices, and supports integration of sensors from variousmanufacturers. Furthermore, lower support costs can be realized becausecall centers, installers, etc. are only required to support onearchitecture. Additionally, there is minimal install cost because onlythe panel is required to be replaced as a result of the configurationflexibility offered by the iHub.

The system takeover configurations described below include but are notlimited to a dedicated wireless configuration, a dedicated wirelessconfiguration that includes a touchscreen, and a fished Ethernetconfiguration. Each of these configurations is described in detailbelow.

FIG. 18 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,under an embodiment. All existing wired and RF sensors remain in place.The iHub is located near the Concord panel, and communicates with thepanel via the 802.11 link, but is not so limited. The iHub managescameras through a built-in 802.11 router. The iHub listens to theexisting RF HW sensors, and relays sensor information to the Concordpanel (emulating the equivalent GE sensor). The wired sensors of thelegacy system are connected to the wired zones on the control panel.

FIG. 19 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,and a GE-iControl Touchscreen, under an embodiment. All existing wiredand RF sensors remain in place. The iHub is located near the Concordpanel, and communicates with the panel via the 802.11 link, but is notso limited. The iHub manages cameras through a built-in 802.11 router.The iHub listens to the existing RF HW sensors, and relays sensorinformation to the Concord panel (emulating the equivalent GE sensor).The wired sensors of the legacy system are connected to the wired zoneson the control panel.

The GE-iControl Touchscreen can be used with either of an 802.11connection or Ethernet connection with the iHub. Because the takeoverinvolves a GE Concord panel (or Simon XT), the touchscreen is always anoption. No extra wiring is required for the touchscreen as it can usethe 4-wire set from the replaced keypad of the legacy system. Thisprovides power, battery backup (through Concord), and data link (RS485Superbus 2000) between Concord and touchscreen. The touchscreen receivesits broadband connectivity through the dedicated 802.11 link to theiHub.

FIG. 20 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel connected to an iHub via anEthernet coupling, under an embodiment. All existing wired and RFsensors remain in place. The iHub is located near the Concord panel, andwired to the panel using a 4-wire SUperbus 2000 (RS485) interface, butis not so limited. The iHub manages cameras through a built-in 802.11router. The iHub listens to the existing RF HW sensors, and relayssensor information to the Concord panel (emulating the equivalent GEsensor). The wired sensors of the legacy system are connected to thewired zones on the control panel.

The takeover installation process is similar to the installation processdescribed above, except the control panel of the legacy system isreplaced; therefore, only the differences with the installationdescribed above are provided here. The takeover approach of anembodiment uses the existing RS485 control interfaces that GE Securityand iControl support with the iHub, touchscreen, and Concord panel. Withthese interfaces, the iHub is capable of automatically enrolling sensorsin the panel. The exception is the leverage of an iControl RF cardcompatible with legacy systems to ‘takeover’ existing RF sensors. Adescription of the takeover installation process follows.

During the installation process, the iHub uses an RF Takeover Card toautomatically extract all sensor IDs, zones, and names from the legacypanel. The installer removes connections at the legacy panel fromhardwired wired sensors and labels each with the zone. The installerpulls the legacy panel and replaces it with the GE Concord panel. Theinstaller also pulls the existing legacy keypad and replaces it witheither a GE keypad or a GE-iControl touchscreen. The installer connectslegacy hardwired sensors to appropriate wired zone (from labels) on theConcord. The installer connects the iHub to the local network andconnects the iHub RS485 interface to the Concord panel. The iHubautomatically ‘enrolls’ legacy RF sensors into the Concord panel as GEsensors (maps IDs), and pushes or otherwise propagates other informationgathered from HW panel (zone, name, group). The installer performs atest of all sensors back to CMS. In operation, the iHub relays legacysensor data to the Concord panel, emulating equivalent GE sensorbehavior and protocols.

The areas of the installation process particular to the legacy takeoverinclude how the iHub extracts sensor info from the legacy panel and howthe iHub automatically enrolls legacy RF sensors and populates Concordwith wired zone information. Each of these areas is described below. Inhaving the iHub extract sensor information from the legacy panel, theinstaller ‘enrolls’ iHub into the legacy panel as a wireless keypad (useinstall code and house ID—available from panel). The iHub legacy RFTakeover Card is a compatible legacy RF transceiver. The installer usesthe web portal to place iHub into ‘Takeover Mode’, and the web portalthe automatically instructs the iHub to begin extraction. The iHubqueries the panel over the RF link (to get all zone information for allsensors, wired and RF). The iHub then stores the legacy sensorinformation received during the queries on the iConnect server.

The iHub also automatically enrolls legacy RF sensors and populatesConcord with wired zone information. In so doing, the installer selects‘Enroll legacy Sensors into Concord’ (next step in ‘Takeover’ process onweb portal). The iHub automatically queries the iConnect server, anddownloads legacy sensor information previously extracted. The downloadedinformation includes an ID mapping from legacy ID to ‘spoofed’ GE ID.This mapping is stored on the server as part of the sensor information(e.g., the iConnect server knows that the sensor is a legacy sensoracting in GE mode). The iHub instructs Concord to go into install mode,and sends appropriate Superbus 2000 commands for sensor learning to thepanel. For each sensor, the ‘spoofed’ GE ID is loaded, and zone, name,and group are set based on information extracted from legacy panel. Uponcompletion, the iHub notifies the server, and the web portal is updatedto reflect next phase of Takeover (e.g., ‘Test Sensors’).

Sensors are tested in the same manner as described above. When a HWsensor is triggered, the signal is captured by the iHub legacy RFTakeover Card, translated to the equivalent GE RF sensor signal, andpushed to the panel as a sensor event on the SuperBus 2000 wires.

In support of remote programming of the panel, CMS pushes newprogramming to Concord over a phone line, or to the iConnect CMS/AlarmServer API, which in turn pushes the programming to the iHub. The iHubuses the Concord Superbus 2000 RS485 link to push the programming to theConcord panel.

FIG. 21 is a flow diagram for automatic takeover 2100 of a securitysystem, under an embodiment. Automatic takeover includes establishing2102 a wireless coupling between a takeover component running under aprocessor and a first controller of a security system installed at afirst location. The security system includes some number of securitysystem components coupled to the first controller. The automatictakeover includes automatically extracting 2104 security data of thesecurity system from the first controller via the takeover component.The automatic takeover includes automatically transferring 2106 thesecurity data to a second controller and controlling loading of thesecurity data into the second controller. The second controller iscoupled to the security system components and replaces the firstcontroller.

FIG. 22 is a flow diagram for automatic takeover 2200 of a securitysystem, under an alternative embodiment. Automatic takeover includesautomatically forming 2202 a security network at a first location byestablishing a wireless coupling between a security system and agateway. The gateway of an embodiment includes a takeover component. Thesecurity system of an embodiment includes security system components.The automatic takeover includes automatically extracting 2204 securitydata of the security system from a first controller of the securitysystem. The automatic takeover includes automatically transferring 2206the security data to a second controller. The second controller of anembodiment is coupled to the security system components and replaces thefirst controller.

Embodiments described herein include a system comprising a securitycoprocessor. The security coprocessor is coupled to a security system ata premises. The security system includes security system components. Thesystem of an embodiment comprises an interactive security system at thepremises coupled to the security coprocessor and to a remote network.The security coprocessor controls communications between the securitysystem and the interactive security system. The interactive securitysystem generates in the premises a subnetwork comprising networkcomponents. The interactive security system controls communicationsbetween the security system components, the network components, and theremote network.

Embodiments described herein include a system comprising: a securitycoprocessor, wherein the security coprocessor is coupled to a securitysystem at a premises, the security system including security systemcomponents; and an interactive security system at the premises coupledto the security coprocessor and to a remote network, wherein thesecurity coprocessor controls communications between the security systemand the interactive security system, the interactive security systemgenerating in the premises a subnetwork comprising network components,wherein the interactive security system controls communications betweenthe security system components, the network components, and the remotenetwork.

The security system of an embodiment is coupled to supply power to thesecurity coprocessor.

The system of an embodiment comprises a power switch coupled to thesecurity system, the security coprocessor, and the interactive securitysystem.

The security system of an embodiment supplies power to the interactivesecurity system via the power switch.

The security system of an embodiment signals the security coprocessor ofan external power failure and, in response, the security coprocessorsignals the power switch to terminate power to the interactive securitysystem.

The interactive security system of an embodiment automaticallyestablishes a coupling with the security system and forms a securitynetwork by electronically integrating communications and functions ofthe network components and the security system components.

The interactive security system of an embodiment comprises an interfacefor control of the security system components and the networkcomponents.

The interactive security system of an embodiment provides access to thecommunications and the functions of the security network via remoteclient devices.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The interactive security system of an embodiment automatically discoversthe security system components.

The interactive security system of an embodiment uses protocols of thesecurity system to discover the security system components.

The interactive security system of an embodiment automaticallyestablishes a coupling with the security system components.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the interactivesecurity system is coupled to the central monitoring station via theremote network that is different than the primary communication link,wherein the central monitoring station is located at a third locationdifferent from the first location and the second location.

The interactive security system of an embodiment transmits event data ofat least one of the security system components and the networkcomponents to the central monitoring station over the remote network.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes in device states ofthe network components, data of the network components, and datareceived by the network components.

The remote network of an embodiment includes a broadband coupling.

The remote network of an embodiment includes a General Packet RadioService (GPRS) coupling.

The interactive security system of an embodiment transmits messagescomprising event data of at least one of the security system componentsand the network components to remote client devices over the remotenetwork.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes in device states ofthe network components, data of the network components, and datareceived by the network components.

The interactive security system of an embodiment receives control datafor control of at least one of the security system components and thenetwork components from remote client devices via the secondarycommunication link.

The interactive security system of an embodiment automatically discoversthe network components.

The interactive security system of an embodiment automatically installsthe network devices in the security network.

The interactive security system of an embodiment receives control datafor control of the network devices from remote client devices.

The network component of an embodiment is an Internet Protocol device.

The network component of an embodiment is a camera.

The network component of an embodiment is a touchscreen.

The network component of an embodiment is a device controller thatcontrols an attached device.

The network component of an embodiment is a sensor.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

The system of an embodiment comprises a touchscreen, wherein theinteractive security system is a component of the touchscreen.

The system of an embodiment comprises segregating via the touchscreendata traffic between the security system, the subnetwork and the remotenetwork, the segregating comprising using separate security and privacypolicies for components coupled to the security system, the subnetworkand the remote network.

The system of an embodiment comprises simultaneously presenting aplurality of interfaces on the touchscreen, the plurality of interfacesincluding a security interface for accessing and controlling thesecurity system and the security system components, wherein the securitysystem interface is ever present in a dedicated region of thetouchscreen.

The plurality of interfaces of an embodiment include a subnetworkinterface for accessing and controlling the network components, and aremote network interface for accessing the remote network.

The system of an embodiment comprises enabling interaction among atleast one of the security system components and the network componentsvia the plurality of interfaces.

The system of an embodiment comprises electronically retrieving contentvia the touchscreen and the remote network, and integrating the contentin at least one of the touchscreen, the security system, the securitysystem components, and the network components, wherein the contentincludes a software application and interactive content in the form ofinternet widgets.

The system of an embodiment comprises an application engine coupled tothe touchscreen, wherein the application engine controls a plurality ofapplications, wherein the plurality of applications includes a residentapplication that manages interactions between the plurality ofapplications.

The resident application of an embodiment determines a priority of eachapplication of the plurality of applications and manages the pluralityof applications according to the priority.

The system of an embodiment comprises a security server at a secondlocation different from the first location, wherein security server iscoupled to the interactive security system.

The interactive security system of an embodiment controls communicationsbetween the network devices, the security system components, and thesecurity server.

The security server of an embodiment performs creation, modification,deletion and configuration of at least one of the security componentsand the network components.

The security server of an embodiment creates automations, schedules andnotification rules associated with at least one of the securitycomponents and the network components.

The security server of an embodiment manages access to current andlogged state data for at least one of the security components and thenetwork components.

The security server of an embodiment manages access to current andlogged state data for couplings between the interactive security systemand at least one of the security components and the network components.

The security server of an embodiment manages communications with atleast one of the security components and the network components.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

Embodiments described herein include a system comprising a securitycoprocessor. The security coprocessor is coupled to a security system ata premises. The security system includes security system components. Thesystem of an embodiment comprises a touchscreen comprising aninteractive security system coupled to the security coprocessor and to aremote network. The security coprocessor controls communications betweenthe security system and the touchscreen. The touchscreen generates inthe premises a subnetwork comprising network components. The touchscreencontrols communications between the security system components, thenetwork components, and the remote network.

Embodiments described herein include a system comprising: a securitycoprocessor, wherein the security coprocessor is coupled to a securitysystem at a premises, the security system including security systemcomponents; and a touchscreen comprising an interactive security systemcoupled to the security coprocessor and to a remote network, wherein thesecurity coprocessor controls communications between the security systemand the touchscreen, the touchscreen generating in the premises asubnetwork comprising network components, wherein the touchscreencontrols communications between the security system components, thenetwork components, and the remote network.

Embodiments described herein include a system comprising a securitycoprocessor. The security coprocessor is coupled to a security system ata premises. The security system includes security system components andis coupled to a central monitoring station via a first communicationlink. The system of an embodiment includes an interactive securitysystem at the premises coupled to the security coprocessor and to aremote network via a second communication link different from the firstcommunication link. The security coprocessor controls communicationsbetween the security system and the interactive security system. Theinteractive security system generates in the premises a subnetworkcomprising network components. The interactive security system controlscommunications between the security system components, the networkcomponents, and the remote network.

Embodiments described herein include a system comprising: a securitycoprocessor, wherein the security coprocessor is coupled to a securitysystem at a premises, the security system including security systemcomponents and coupled to a central monitoring station via a firstcommunication link; and an interactive security system at the premisescoupled to the security coprocessor and to a remote network via a secondcommunication link different from the first communication link, whereinthe security coprocessor controls communications between the securitysystem and the interactive security system, the interactive securitysystem generating in the premises a subnetwork comprising networkcomponents, wherein the interactive security system controlscommunications between the security system components, the networkcomponents, and the remote network.

Embodiments described herein include a method comprising generating asecurity network at a premises by coupling a security coprocessor to asecurity system and to an interactive security system. The securitysystem includes security system components. The interactive securitysystem is coupled to a remote network. The method of an embodimentcomprises controlling communications between the security system and theinteractive security system with the security coprocessor. The method ofan embodiment comprises generating with the interactive security systema subnetwork in the premises comprising network components. The methodof an embodiment comprises controlling communications between thesecurity system components, the network components, and the remotenetwork with the interactive security system.

Embodiments described herein include a method comprising: generating asecurity network at a premises by coupling a security coprocessor to asecurity system and to an interactive security system, wherein thesecurity system includes security system components, wherein theinteractive security system is coupled to a remote network; controllingcommunications between the security system and the interactive securitysystem with the security coprocessor; generating with the interactivesecurity system a subnetwork in the premises comprising networkcomponents; and controlling communications between the security systemcomponents, the network components, and the remote network with theinteractive security system.

The method of an embodiment comprises supplying power to the securitycoprocessor from the security system.

The method of an embodiment comprises coupling a power switch to thesecurity system, the security coprocessor, and the interactive securitysystem.

The method of an embodiment comprises supplying power to the interactivesecurity system from the security system via the power switch.

The method of an embodiment comprises receiving a signal at the securitycoprocessor from the security system signaling of an external powerfailure and, in response, signaling the power switch to terminate powerto the interactive security system.

The method of an embodiment comprises forming the interactive securitysystem as a component of a touchscreen.

The method of an embodiment comprises segregating via the touchscreendata traffic between the security system, the subnetwork and the remotenetwork, the segregating comprising using separate security and privacypolicies for components coupled to the security system, the subnetworkand the remote network.

The method of an embodiment comprises simultaneously presenting aplurality of interfaces on the touchscreen, the plurality of interfacesincluding a security interface for accessing and controlling thesecurity system and the security system components, wherein the securitysystem interface is ever present in a dedicated region of thetouchscreen.

The plurality of interfaces of an embodiment includes a subnetworkinterface for accessing and controlling the network components, and aremote network interface for accessing the remote network.

The method of an embodiment comprises enabling interaction among atleast one of the security system components and the network componentsvia the plurality of interfaces.

The method of an embodiment comprises electronically retrieving contentvia the touchscreen and the remote network, and integrating the contentin at least one of the touchscreen, the security system, the securitysystem components, and the network components, wherein the contentincludes a software application and interactive content in the form ofinternet widgets.

The method of an embodiment comprises an application engine coupled tothe touchscreen, wherein the application engine controls a plurality ofapplications, wherein the plurality of applications includes a residentapplication that manages interactions between the plurality ofapplications.

The resident application of an embodiment determines a priority of eachapplication of the plurality of applications and manages the pluralityof applications according to the priority.

The method of an embodiment comprises the interactive security systemautomatically establishing a coupling with the security system andforming a security network by electronically integrating communicationsand functions of the network components and the security systemcomponents.

The method of an embodiment comprises presenting a control interfacethrough the interactive security system for control of the securitysystem components and the network components.

The method of an embodiment comprises accessing with remote clientdevices the communications and the functions of the security network viathe interactive security system.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The interactive security system of an embodiment automatically discoversthe security system components.

The interactive security system of an embodiment uses protocols of thesecurity system to discover the security system components.

The interactive security system of an embodiment automaticallyestablishes a coupling with the security system components.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the interactivesecurity system is coupled to the central monitoring station via theremote network that is different than the primary communication link,wherein the central monitoring station is located at a third locationdifferent from the first location and the second location.

The interactive security system of an embodiment transmits event data ofat least one of the security system components and the networkcomponents to the central monitoring station over the remote network.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes in device states ofthe network components, data of the network components, and datareceived by the network components.

The remote network of an embodiment includes a broadband coupling.

The remote network of an embodiment includes a General Packet RadioService (GPRS) coupling.

The interactive security system of an embodiment transmits messagescomprising event data of at least one of the security system componentsand the network components to remote client devices over the remotenetwork.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes in device states ofthe network components, data of the network components, and datareceived by the network components.

The interactive security system of an embodiment receives control datafor control of at least one of the security system components and thenetwork components from remote client devices via the secondarycommunication link.

The interactive security system of an embodiment automatically discoversthe network components.

The interactive security system of an embodiment automatically installsthe network devices in the security network.

The interactive security system of an embodiment receives control datafor control of the network devices from remote client devices.

The network component of an embodiment is at least one of an InternetProtocol device, a camera, a touchscreen, a device controller thatcontrols an attached device, a sensor.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

The method of an embodiment comprises coupling a security server at asecond location to the interactive security system, wherein the secondlocation is different from the first location.

The method of an embodiment comprises controlling via the interactivesecurity system communications between the network devices, the securitysystem components, and the security server.

The security server of an embodiment creates, modifies, deletes andconfigures at least one of the security components and the networkcomponents.

The security server of an embodiment creates automations, schedules andnotification rules associated with at least one of the securitycomponents and the network components.

The security server of an embodiment manages access to current andlogged state data for at least one of the security components and thenetwork components.

The security server of an embodiment manages access to current andlogged state data for couplings between the interactive security systemand at least one of the security components and the network components.

The security server of an embodiment manages communications with atleast one of the security components and the network components.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The integrated security system can be a component of a single system,multiple systems, and/or geographically separate systems. The integratedsecurity system can also be a subcomponent or subsystem of a singlesystem, multiple systems, and/or geographically separate systems. Theintegrated security system can be coupled to one or more othercomponents (not shown) of a host system or a system coupled to the hostsystem.

One or more components of the integrated security system and/or acorresponding system or application to which the integrated securitysystem is coupled or connected includes and/or runs under and/or inassociation with a processing system. The processing system includes anycollection of processor-based devices or computing devices operatingtogether, or components of processing systems or devices, as is known inthe art. For example, the processing system can include one or more of aportable computer, portable communication device operating in acommunication network, and/or a network server. The portable computercan be any of a number and/or combination of devices selected from amongpersonal computers, personal digital assistants, portable computingdevices, and portable communication devices, but is not so limited. Theprocessing system can include components within a larger computersystem.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the integrated securitysystem can be located together or in separate locations. Communicationpaths couple the components and include any medium for communicating ortransferring files among the components. The communication paths includewireless connections, wired connections, and hybrid wireless/wiredconnections. The communication paths also include couplings orconnections to networks including local area networks (LANs),metropolitan area networks (MANs), wide area networks (WANs),proprietary networks, interoffice or backend networks, and the Internet.Furthermore, the communication paths include removable fixed mediumslike floppy disks, hard disk drives, and CD-ROM disks, as well as flashRAM, Universal Serial Bus (USB) connections, RS-232 connections,telephone lines, buses, and electronic mail messages.

Aspects of the integrated security system and corresponding systems andmethods described herein may be implemented as functionality programmedinto any of a variety of circuitry, including programmable logic devices(PLDs), such as field programmable gate arrays (FPGAs), programmablearray logic (PAL) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits (ASICs). Some other possibilities for implementingaspects of the integrated security system and corresponding systems andmethods include: microcontrollers with memory (such as electronicallyerasable programmable read only memory (EEPROM)), embeddedmicroprocessors, firmware, software, etc. Furthermore, aspects of theintegrated security system and corresponding systems and methods may beembodied in microprocessors having software-based circuit emulation,discrete logic (sequential and combinatorial), custom devices, fuzzy(neural) logic, quantum devices, and hybrids of any of the above devicetypes. Of course the underlying device technologies may be provided in avariety of component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the integrated security systemand corresponding systems and methods is not intended to be exhaustiveor to limit the systems and methods to the precise forms disclosed.While specific embodiments of, and examples for, the integrated securitysystem and corresponding systems and methods are described herein forillustrative purposes, various equivalent modifications are possiblewithin the scope of the systems and methods, as those skilled in therelevant art will recognize. The teachings of the integrated securitysystem and corresponding systems and methods provided herein can beapplied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the integrated security system and corresponding systems andmethods in light of the above detailed description.

1. A method comprising: determining, by a device application on acomputing device, a priority of a plurality of applications on thecomputing device, wherein the plurality of applications are associatedwith a plurality of premises devices of a premises management system;and managing, by the device application and based on the priority, oneor more interactions between the plurality of applications on thecomputing device.
 2. The method of claim 1, wherein the managing the oneor more interactions comprises at least one of responding to one or moreresource requests, processing one or more resource requests, monitoringapplication behavior, or responding to one or more requests for a. cacheupdate.
 3. The method of claim 2, wherein the one or more resourcerequests are associated with at least one of memory, caching, power,application version management, application updates, or caching orsynchronizing user preferences.
 4. The method of claim 1, wherein theplurality of premises devices comprises at least one of a camera, athermostat control, an energy control, a door locking mechanism, alighting control, a door sensor, a window sensor, a motion sensor, aglass break detector, a. smoke detector, a fire sensor, or a floodsensor.
 5. The method of claim 1, wherein the plurality of applicationscomprise at least one of a maintenance and service application, a cameraapplication, a thermostat application, an energy application, a doorapplication, a window application, a lighting application, a motionsensor application, a glass break detector application, a smoke detectorapplication, a fire sensor application, or a flood sensor application 6.The method of claim 1, wherein the computing device and the pluralitypremises devices are located at a premises.
 7. The method of claim 6,wherein the premises management system comprises at least one of asecurity system or a home automation system located at the premises. 8.A non-transitory computer-readable medium comprising instructions that,when executed, cause: determining, by a device application on acomputing device, a priority of a plurality of applications on thecomputing device, wherein the plurality of applications are associatedwith a plurality of premises devices of a premises management system;and managing, by the device application and based on the priority, oneor more interactions between the plurality of applications on thecomputing device.
 9. The non-transitory computer-readable medium ofclaim 8, wherein the instructions that cause the managing the one ormore interactions cause at least one of responding to one or moreresource requests, processing one or more resource requests, monitoringapplication behavior, or responding to one or more requests for a cacheupdate.
 10. The non-transitory computer-readable medium of claim 9,wherein the one or more resource requests is associated with at leastone of memory, caching, power, application version management,application updates, or caching or synchronizing user preferences. 11.The non-transitory computer-readable medium of claim 8, wherein theplurality of premises devices comprises at least one of a camera, athermostat control, an energy control, a door locking mechanism, alighting control, a door sensor, a window sensor, a motion sensor, aglass break detector, a smoke detector, a fire sensor, or a floodsensor.
 12. The non-transitory computer-readable medium of claim 8,wherein the plurality of applications comprise at least one of amaintenance and service application, a camera application, a thermostatapplication, an energy application, a door application, a windowapplication, a lighting application, a motion sensor application, aglass break detector application, a smoke detector application, a firesensor application, or a flood sensor application.
 13. Thenon-transitory computer-readable medium of claim 8, wherein thecomputing device and the plurality of premises devices are located at apremises.
 14. The non-transitory computer-readable: medium of claim 13,wherein the premises management system comprises at least one of asecurity system or a home automation system located at the premises. 15.A computing device comprising: one or more processors; and instructions,that when executed by the one or more processors, cause the computingdevice to: determine, by a device application on the computing device, apriority of a plurality of applications on the computing device, whereinthe plurality of applications are associated with a plurality ofpremises devices of a premises management system; and manage, by thedevice application and based on the priority, one or more interactionsbetween the plurality of applications on the computing device.
 16. Thecomputing device of claim 15, wherein the instructions that cause thecomputing device to manage the one or more interactions cause thecomputing device to at least one of responding to one or more resourcerequests, processing one or more resource requests, monitoringapplication behavior, or responding to one or more requests for a cacheupdate.
 17. The computing device of claim 16, wherein the resourcerequest is associated with at least one of memory, caching, power,application version management, application updates, or caching orsynchronizing user preferences.
 18. The computing device of claim 15,wherein the plurality of premises devices comprises at least one of acamera, a thermostat control, an energy control, a door lockingmechanism, a lighting control, a door sensor, a window sensor, a motionsensor, a glass break detector, a smoke detector, a fire sensor, or aflood sensor.
 19. The computing device of claim 15, wherein theplurality of applications comprise at least one of a maintenance andservice application, camera application, a thermostat application, anenergy application, a door application, a window application, a lightingapplication, a motion sensor application, a glass break detectorapplication, a smoke detector application, a fire sensor application, ora flood sensor application.
 20. The computing device of claim 15,wherein the computing device and the plurality of premises devices arelocated at a premises.